home *** CD-ROM | disk | FTP | other *** search
- KISS Proms for use with TheNode.
-
- Several PROM images are supplied for for use with TNC2 (or clones), and one
- for use with the TNC220.
-
-
- KISS is as released with the TCPIP package. I have used this code, and
- it seems to work, but it does have loopholes in its buffer management. As
- I have experienced buffering problems with other KISS mode TNCs with TheNode,
- i've done a version which will reset if it runs out. This is a bit drastic,
- but should keep the system going. (Higher level software will retry the
- discarded messages). If it improves things, I'll refine it to discard the
- oldest. The new eprom image is in the file JKISS.
-
-
-
- 220KISS is a version of JKISS, modified to run on the TNC220. This version
- only supports the VHF port (port 2) at 1200 baud,and the aync link to the PC
- is fixed at 2400. The DCD led is driven by software, but is controlled by the
- DCD signal from the modem (ie DCD processing is the same as with the TNC2 -
- the SOFTDCD mode of the 220 is not implemented). Other versions are possible
- if there is sufficient interest - the main problem is that the KISS command
- set would have to be extended to include commands for port and speed switching.
-
- Note the software is now set up to run with the clock speed jumper in the
- 'Low' speed position - several people have had problems running in the 'Fast'
- mode.
-
-
- BPQKISS - A Multidropped KISS system. (TNC2 and clones only)
-
- I have implemented a system to allow more than one KISS-like TNC to connect
- to a single Async port. This is primarily for those running machines with
- little expansion capability, but can also enable the TNCs and transceivers
- to be located remotely from the PC with a simple 3 wire link. This could be
- useful on the lower frequencies, where QRM from the PC blocks the receiver
- ( I have real problems running a 50meg RX near the PC). A simple checksum
- is also added to each packet, to reduce the risk of corruption if running on
- long leads (or even over a modem link).
-
-
- The system uses polling to prevent contention on the link. Each TNC must
- run the BPQKISS program, and each must have a different 'address' byte
- patched in at location 20hex. In the PORTS section of BPQCFG.TXT, PROTOCOL
- must be set to KISS, KISSOPTIONS to POLLED,CHECKSUM,ACKMODE and CHANNEL
- set to correspond to the address in the PROM -
-
- CHANNEL Address (in byte 20h of PROM)
-
- A 00h
- B 10h
- C 20h
- D 30h etc
-
- In theory you can have up to 16, but in practice the maximum will depend
- on the power of the PC and the speed of the radio ports.
-
-
- Wiring.
-
- PC TNC 1 TNC 2
-
- GROUND 7 ---------------7----------------7----------- etc
-
- TXD 2 ---------------2----------------2----------- etc
-
- RXD 3 -------------------------------------------- etc
- | |
- - -
- ^ ^
- | |
- 3 3
-
- -
- ^ is a diode (1N914 or similar)
-
-
- With some TNCs and serial cards, a pulldown resistor may be required
- from pin 3 on the PC (10k to -12v is suggested). Thanks to G3ZFJ for this
- information.
-
-
-
- The protocol used for this multidropped option was changed from version 3.59a
- onwards to be compatible with similar software produced by KANTRONICS for their
- range of TNCs. The new version is called BPQKISS, and replaces the old JKISSP.
-
- For those of you unfamiliar with KISS TNCs, the STA led indicates frames
- being received from the PC and the CON led frames being sent to the PC. On
- powerup, some LEDS should flash about 3 times - which ones depends on the
- version and the RAM size in the TNC.
-
-
-
- CWID
-
-
- I have added CWID to my JKISS and BPQKISS EPROMs. The Callsign to be sent
- is patched into the EPROM image with the program PATCHID, which takes two
- parameters, the required callsign, and the file to patch (either JKISS or
- BPQKISS). Note that the specified file is overwritten, so I suggest you
- make a copy of the original first.
-
-
- PATCHID G8BPQ JKISS - Note call must be in upper case
-
-
- The CW patttern which will be sent is displayed on the screen - please
- check it, just in case my translate table is wrong!
-
- The ID is sent after one minute, then at 29 minute intervals, with a dot
- length of 60ms. If my calculations are correct, this equates to 20 WPM
-
- The ID is send in AFSK (assuming a normal AFSK modem), but because of the
- hardware design it is not possible to control which tone corresponds to
- mark or space - it depends on what was sent just before the ID starts.
- If you are using a modem with a scrambler (eg G3RUH), then the system
- wont work - the two tones will sound the same. I'd like to know if a
- CWID facility for RUH modems would be useful - if there is a significant
- demand I'll see if I can find a solution. A simple on-off keying may be
- possible, but would depend on the PTT characteristics of the TX. If you
- have a better idea, please let me know!
-
-
- The normal SLOTTIME/PERSISTENCE code is used to minimise collisions with
- other stations (hence the interval of 29 mins, allowing a bit of time for
- congestion, without going over the statutory 30 mins interval).
-
-
-
- John Wiseman, G8BPQ
- 7 March 1991
-